Skip to content

Rollup of 5 pull requests - #161347

Merged
rust-bors[bot] merged 81 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-uv2vd9y
Aug 19, 2026
Merged

Rollup of 5 pull requests#161347
rust-bors[bot] merged 81 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-uv2vd9y

Conversation

@JonathanBrouwer

@JonathanBrouwer JonathanBrouwer commented Aug 19, 2026

Copy link
Copy Markdown
Member

Successful merges:

r? @ghost

Create a similar rollup

aland-omed and others added 30 commits July 22, 2026 03:59
Signed-off-by: Aland <158173939+aland-omed@users.noreply.github.com>
- Update a link to MCU list in the code and make it an actual link
- Make avr-tester link point to the crate page (which is more expected
  and informative) instead of a repository (which has also moved)
`./x` was duplicated; the explanation of when to use alternatives was
not quite correct; and the intro sentence was also slightly inaccurate.
Give better examples of how to run `x`
fix some typos and update some links
This makes it easy for us to see as maintainers what needs an owner,
and helps people reading the guide a little bit so they don't get excited then disappointed.
…ir-macro-docs

Add documentation for some `rustc_type_ir` macros
Explicitly mark stub chapters in the table of contents
- delete `inline-asm` and redirect it to `asm`
- rename `optional-x86_64-gnu-parallel-frontend` to include the
  `optional-`, matching rl/r
- add a redirect from `/llm-guidance/` to `/llm-guidance`, i think
  there's some docs floating around that accidentally suggest the
  former.
- Remove duplicate "chicken-and-egg" explanation.
  It only needs to be in one place.
- Change most references from `x.py` to `./x`, "bootstrap", or `bootstrap.py` as appropriate.
  Keep the ones where `x.py` is load-bearing.
- Remove over-long and duplicated instructions around the bootstrap wrappers
Update offload docs for macro and third pass
This updates the rust-version file to 2c39ff4.
md links work on both Github and in the published site, whereas html
links only work on the published site.

Update `mdbook-linkcheck2` to the latest version, which supports a new
`require-md-extension` option; enable that option; then fix all the
errors.
…s, r=Kobzol"

This reverts commit 5d4e11e, reversing
changes made to 71b938c.
Document debuginfo `repr` directive
…ce-folder-2473

docs: Clarify Neovim workspace path setup
Add a hint about unflatten and an internal link to MIR outlives graphs to advertise them better.
…malized-ty-return, r=khyperia

Make const eval return normalized ty

closes: rust-lang/trait-system-refactor-initiative#286
closes: rust-lang#156294

r? @lcnr
…h726

Fix a couple of links in AVR target documentation

- Update a link to MCU list in the code and make it an actual link
- Make avr-tester link point to the crate page (which is more expected and informative) instead of a repository (which has also moved)
…anitizers, r=mu001999

compiler: Account for default_sanitizers when comparing target modifiers

Prior to this PR, rustc would complain about mismatched ABIs if crates built with -Zsanitizer=shadow-call-stack were mixed with crates not built with -Zsanitizer=shadow-call-stack for the exact same target where SCS is one of the default_sanitizers. Rustc should also take into account default_sanitizers before doing the target modifiers checks.

AI: Gemini was used to initially help write tests for this PR. I edited some of it and reviewed it to the best of my ability before submitting.
rustc-dev-guide subtree update

Subtree update of `rustc-dev-guide` to rust-lang/rustc-dev-guide@5613bfe.

Created using https://github.com/rust-lang/josh-sync.

r? @ghost
@rust-bors rust-bors Bot added the rollup A PR which is a rollup label Aug 19, 2026
@rustbot rustbot added A-CI Area: Our Github Actions CI A-rustc-dev-guide Area: rustc-dev-guide A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. WG-trait-system-refactor The Rustc Trait System Refactor Initiative (-Znext-solver) labels Aug 19, 2026
@JonathanBrouwer

Copy link
Copy Markdown
Member Author

@bors r+ p=5

@rust-bors

rust-bors Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

📌 Commit 07337b4 has been approved by JonathanBrouwer

It is now in the queue for this repository.

@rust-bors rust-bors Bot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Aug 19, 2026
@rust-bors

This comment has been minimized.

@rust-bors rust-bors Bot added merged-by-bors This PR was explicitly merged by bors. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Aug 19, 2026
@rust-bors

rust-bors Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

☀️ Test successful - CI
Approved by: JonathanBrouwer
Duration: 3h 6m 14s
Pushing f7d782a to main...

@rust-bors
rust-bors Bot merged commit f7d782a into rust-lang:main Aug 19, 2026
14 checks passed
@rustbot rustbot added this to the 1.100.0 milestone Aug 19, 2026
@github-actions

Copy link
Copy Markdown
Contributor
What is this? This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing 407371f (parent) -> f7d782a (this PR)

Test differences

Show 36 test diffs

Stage 1

  • [ui (polonius)] tests/ui/target_modifiers/sanitizer_default.rs#explicit_default: [missing] -> pass (J1)
  • [ui (polonius)] tests/ui/target_modifiers/sanitizer_default.rs#explicit_mismatch: [missing] -> pass (J1)
  • [ui (polonius)] tests/ui/target_modifiers/sanitizer_default.rs#implicit_default: [missing] -> pass (J1)
  • [ui (polonius)] tests/ui/target_modifiers/sanitizer_default.rs#implicit_mismatch: [missing] -> pass (J1)
  • [ui (polonius)] tests/ui/traits/next-solver/adt-const-param-projection.rs#next: [missing] -> pass (J1)
  • [ui (polonius)] tests/ui/traits/next-solver/adt-const-param-projection.rs#old: [missing] -> pass (J1)
  • [ui (polonius)] tests/ui/traits/next-solver/normalize-const-item-type.rs: [missing] -> pass (J1)
  • [ui] tests/ui/target_modifiers/sanitizer_default.rs#explicit_default: [missing] -> pass (J3)
  • [ui] tests/ui/target_modifiers/sanitizer_default.rs#explicit_mismatch: [missing] -> pass (J3)
  • [ui] tests/ui/target_modifiers/sanitizer_default.rs#implicit_default: [missing] -> pass (J3)
  • [ui] tests/ui/target_modifiers/sanitizer_default.rs#implicit_mismatch: [missing] -> pass (J3)
  • [ui] tests/ui/traits/next-solver/adt-const-param-projection.rs#next: [missing] -> pass (J3)
  • [ui] tests/ui/traits/next-solver/adt-const-param-projection.rs#old: [missing] -> pass (J3)
  • [ui] tests/ui/traits/next-solver/normalize-const-item-type.rs: [missing] -> pass (J3)

Stage 2

  • [ui] tests/ui/target_modifiers/sanitizer_default.rs#explicit_default: [missing] -> pass (J0)
  • [ui] tests/ui/target_modifiers/sanitizer_default.rs#explicit_mismatch: [missing] -> pass (J0)
  • [ui] tests/ui/target_modifiers/sanitizer_default.rs#implicit_default: [missing] -> pass (J0)
  • [ui] tests/ui/target_modifiers/sanitizer_default.rs#implicit_mismatch: [missing] -> pass (J0)
  • [ui] tests/ui/target_modifiers/sanitizer_default.rs#explicit_default: [missing] -> ignore (gcc backend is marked as ignore) (J2)
  • [ui] tests/ui/target_modifiers/sanitizer_default.rs#explicit_mismatch: [missing] -> ignore (gcc backend is marked as ignore) (J2)
  • [ui] tests/ui/target_modifiers/sanitizer_default.rs#implicit_default: [missing] -> ignore (gcc backend is marked as ignore) (J2)
  • [ui] tests/ui/target_modifiers/sanitizer_default.rs#implicit_mismatch: [missing] -> ignore (gcc backend is marked as ignore) (J2)
  • [ui] tests/ui/traits/next-solver/adt-const-param-projection.rs#next: [missing] -> pass (J4)
  • [ui] tests/ui/traits/next-solver/adt-const-param-projection.rs#old: [missing] -> pass (J4)
  • [ui] tests/ui/traits/next-solver/normalize-const-item-type.rs: [missing] -> pass (J4)

Additionally, 11 doctest diffs were found. These are ignored, as they are noisy.

Job group index

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard f7d782a3be46d6bb4b9792fe69a61db389ba1769 --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

  1. i686-msvc-1: 1h 43m -> 3h 4m (+77.8%)
  2. x86_64-gnu-stdlib-semver-check: 10m 35s -> 18m 49s (+77.8%)
  3. x86_64-gnu-llvm-22-3: 1h 16m -> 1h 54m (+50.4%)
  4. dist-sparcv9-solaris: 1h 8m -> 1h 41m (+47.7%)
  5. dist-i686-msvc: 2h 18m -> 1h 35m (-30.9%)
  6. x86_64-msvc-2: 1h 28m -> 1h 54m (+30.3%)
  7. i686-msvc-2: 2h 12m -> 1h 37m (-26.8%)
  8. x86_64-gnu-llvm-21-3: 1h 24m -> 1h 46m (+25.0%)
  9. test-various: 1h 57m -> 1h 29m (-23.8%)
  10. x86_64-gnu-parallel-frontend: 1h 38m -> 2h 1m (+23.5%)
How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

@rust-timer

Copy link
Copy Markdown
Collaborator

Finished benchmarking commit (f7d782a): comparison URL.

Overall result: ❌ regressions - no action needed

@rustbot label: -perf-regression

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
1.1% [1.1%, 1.1%] 1
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) - - 0

Max RSS (memory usage)

Results (secondary 3.0%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
3.0% [3.0%, 3.0%] 1
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) - - 0

Cycles

This perf run didn't have relevant results for this metric.

Binary size

Results (primary -0.0%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-0.0% [-0.0%, -0.0%] 2
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) -0.0% [-0.0%, -0.0%] 2

Bootstrap: 458.213s -> 456.256s (-0.43%)
Artifact size: 399.03 MiB -> 398.95 MiB (-0.02%)

@rust-bors

rust-bors Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#161218 Revert "Rollup merge of #161006 - GuillaumeGomez:gcc-binuti… c15176be2a8b59d11e4062959c72cf273cd33c77
(link)
#160526 Make const eval return normalized ty 8d188b533e2753afc10a2b6490b71739c2882d78
(link)
#160460 Fix a couple of links in AVR target documentation 3ea726e28e44fd1c90c58902ababd38da63d12c6
(link)
#161333 compiler: Account for default_sanitizers when comparing tar… f1f6ef39b5b3d8de61f99d0086b7976af904a548
(link)
#161343 rustc-dev-guide subtree update 1ba4d77b30fc0d66885a35149658f511d2511c01
(link)

parent commit: 407371fb75

In the case of a perf regression, run the following command for each PR you suspect might be the cause: @rust-timer build $SHA

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-CI Area: Our Github Actions CI A-rustc-dev-guide Area: rustc-dev-guide A-testsuite Area: The testsuite used to check the correctness of rustc merged-by-bors This PR was explicitly merged by bors. rollup A PR which is a rollup T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. WG-trait-system-refactor The Rustc Trait System Refactor Initiative (-Znext-solver)

Projects

None yet

Development

Successfully merging this pull request may close these issues.